[Bug Fix] Fix the element size calculation in AeroAcoustics module#3133
[Bug Fix] Fix the element size calculation in AeroAcoustics module#3133andrew-platt merged 3 commits intoOpenFAST:devfrom
Conversation
On last node, the element size was calculated as half the distance in span between the last two nodes. This should not be divided by 2.
|
This has a relatively large impact on the measurements for |
|
|
hi @bjonkman and @andrew-platt. thank you for your patience. I've finally had the time to run some checks, rerunning the Case 1.1 from this this conference paper, see Figure 7, and this technical report, see Figure 41. The summary is that this PR changes the results minimally. These are the results from the conference paper. I generated those in 2021 running OpenFAST v3.0.0 (or possibly a dev branch around that time) This is the comparison today between v3.0.0, v4.1.2, and v4.2.0. The first two match exactly, the second is slightly different 
Please let me know if you'd like to see more checks |
3 participants
Feature or improvement description
On last node (at the tip), the element size for aeroacoustics calculations was calculated as half the difference in span locations between the last two nodes. This should not be divided by 2.
Related issue, if one exists
Impacted areas of the software
AeroAcoustics only
Test results, if applicable
The AeroAcoustics regression test,
IEA_LB_RWT-AeroAcousticsfails. Here are some of the failing channels: